Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[O11y][MongoDB] Migrate Logs Overview dashboard visualizations to lens in kibana 8.1.0 #5831

Merged
merged 3 commits into from
Apr 11, 2023
Merged

[O11y][MongoDB] Migrate Logs Overview dashboard visualizations to lens in kibana 8.1.0 #5831

merged 3 commits into from
Apr 11, 2023

Conversation

rajvi-patel-22
Copy link
Contributor

  • Enhancement

What does this PR do?

  • Migrate visualizations to lens for MongoDB integration package

  • Statistics for MongoDB Lens migration:

MongoDB dashboard Before Migration   After Migration  
  Lens Visualization Lens Visualization
[Logs MongoDB] Overview 0 1 1 0
  0 1 1 0

Checklist

  • I have added an entry to my package's changelog.yml file.
  • I have verified that panels are populated with data.
  • I have verified that panels are not distorted after being migrated to lens.
  • I have updated screenshots of dashboard.
  • I have verified that data count are matching and panel aggregations are same as before.

Author's Checklist

  • Migrated panels should be removed from visualization folder.
  • Migrated visualizations are populating in current Kibana version 8.1.0 itself.

Related issues

Note: The Kibana files and screenshot of dashboard are not synced. Please find below image to compare before and after migration visualizations.

screencapture-storage-0-kb-us-central1-gcp-cloud-es-io-9243-app-dashboards-2023-03-15-12_03_41 (1)

@rajvi-patel-22 rajvi-patel-22 requested a review from a team as a code owner April 10, 2023 13:37
@rajvi-patel-22 rajvi-patel-22 mentioned this pull request Apr 10, 2023
Closed
6 tasks
@kush-elastic kush-elastic added enhancement New feature or request Integration:mongodb MongoDB v8.1.0 Team:Service-Integrations Label for the Service Integrations team labels Apr 10, 2023
@elasticmachine
Copy link

elasticmachine commented Apr 10, 2023 •
edited
Loading

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-04-11T09:12:29.862+0000

  • Duration: 18 min 35 sec

Test stats 🧪

Test Results
Failed 0
Passed 24
Skipped 0
Total 24

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

elasticmachine commented Apr 10, 2023 •
edited
Loading

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (3/3) 💚 50.0
Classes 100.0% (3/3) 💚 50.0
Methods 96.97% (32/33) 👍 26.97
Lines 68.217% (88/129) 👎 -2.017
Conditionals 100.0% (0/0) 💚

@agithomas
Copy link
Contributor

The second column in the visualisation is completely empty. Any specific reason?

@agithomas
Copy link
Contributor

Please complete the PR review

@agithomas
Copy link
Contributor

In the screenshot shared, there exist a log_level having type 'E'. I anticipate it is for Errors. But, the Error log panel shows no record which is not logically correct. Please check the feature / data , used for generating the screenshot

@rajvi-patel-22
Copy link
Contributor Author

In the screenshot shared, there exist a log_level having type 'E'. I anticipate it is for Errors. But, the Error log panel shows no record which is not logically correct. Please check the feature / data , used for generating the screenshot

@agithomas, Logs Severity panel has filter log.level: * whereas Error logs panel has filter log.level: F or log.level: W. That is the reason Error logs doesn't show any data.

@rajvi-patel-22
Copy link
Contributor Author

The second column in the visualisation is completely empty. Any specific reason?

@agithomas, If you are talking about the mongodb.log.timestamp column then please find this segment of pipeline which removes mongodb.log.timestamp field. I think dashboards are not updated after pipeline modification.

@agithomas
Copy link
Contributor

this

Can you please create a backlog issue for this ? Please share the link here after creating the backlog issue

@rajvi-patel-22
Copy link
Contributor Author

this

Can you please create a backlog issue for this ? Please share the link here after creating the backlog issue

@agithomas, I have created the backlog issue.

agithomas
agithomas approved these changes Apr 11, 2023
View reviewed changes
Copy link
Contributor

@agithomas agithomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@kush-elastic kush-elastic merged commit a9a23c8 into elastic:main Apr 11, 2023
@elasticmachine
Copy link

Package mongodb - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=mongodb

@milan-elastic milan-elastic mentioned this pull request Jun 6, 2023
Closed
5 tasks
This was referenced Jun 9, 2023
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@agithomas agithomas agithomas approved these changes

@milan-elastic milan-elastic milan-elastic approved these changes

Assignees

@rajvi-patel-22 rajvi-patel-22

Labels
enhancement New feature or request Integration:mongodb MongoDB Team:Service-Integrations Label for the Service Integrations team v8.1.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@rajvi-patel-22 @elasticmachine @agithomas @milan-elastic @kush-elastic